Keep cufile.log out of the Java source tree - #2553
Merged
rapids-bot[bot] merged 2 commits intoSep 9, 2026
Merged
Conversation
imotov
added
bug
cjnolet
approved these changes
Sep 8, 2026
cuFile writes cufile.log into the JVM's working directory, leaving a stray file in java/cuvs-java and java/cuvs-lucene after every test run. Point CUFILE_LOGFILE_PATH at target/ in the failsafe and surefire forks, and gitignore the file for the example and benchmark modules, which are launched as bare JVMs and so aren't covered by the plugin config. Follow-up to NVIDIA#2257
imotov
force-pushed
the
move-cufile-during-java-tests
branch
from
September 8, 2026 23:14
6443c36 to
c12bc39
Compare
Contributor
Author
|
/merge |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
cuFile writes cufile.log into the JVM's working directory, leaving a stray file in java/cuvs-java and java/cuvs-lucene after every test run. Point CUFILE_LOGFILE_PATH at target/ in the failsafe and surefire forks, and gitignore the file for the example and benchmark modules, which are launched as bare JVMs and so aren't covered by the plugin config.
Follow-up to #2257